-----------------------------------------------------
Guardant Drivers Version 4.81
Copyright (c) 1997-2004 Aktiv Co.
All Rights Reserved.
-----------------------------------------------------


Guardant drivers are needed for safe and stable running 
of protected applications, as well as for all utilities 
working with dongles. Use of drivers helps to avoid 
possible conflicts of sharing resources of the parallel 
or USB ports when accessing the dongle.

This file describes the installation procedures for all 
Guardant drivers.

-----------------------------------------------------
        Contents
-----------------------------------------------------

1     File List
2     Guardant Driver Installation/Update 
3     Guardant Driver Configuration 
4     Guardant Driver Uninstall
5     INSTDRV Command Line Options and Error Codes
6     Problem Reports

-----------------------------------------------------
1     File List
-----------------------------------------------------



File list for Windows 95/98/Me:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 INSTDRV.EXE  - Driver installation utility.
 NVKEY95.VX_  - Windows 95/98/ME driver
 NVKEYU95.SYS - Windows 95 OSR 2.x USB driver
 NVKEYUSB.SYS - USB driver
 NVKEY98U.SYS - Windows 98/Me USB driver
 GSNUSB.IN_   - Driver INF file for USB drivers
 INSTDRV.INI  - Default configuration file
 GRDDEM32.EXE - Demo diagnostic utility
 GRDCTL32.DLL - Diagnostic utility component	
 GRDDRV32.CPL - Guardant Control Panel Applet
 GRDDRV32.DLL - Driver management library (equivalent to instdrv.dll)

File list for Windows NT/2000/XP:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 INSTDRV.EXE  - Driver installation utility.
 NVKEYNT.SYS  - Windows 2000/XP kernel driver
 NVKEYNT4.SYS - Windows NT kernel driver
 NVKEYVDD.DLL - Virtual DOS driver
 NVKEY4NT.SYS - Windows NT/2000/XP DOS device driver
 NVKEYUSB.SYS - USB driver
 GSNUSB.IN_   - Driver INF file for USB drivers
 INSTDRV.INI  - Default configuration file
 GRDDEM32.EXE - Demo diagnostic utility
 GRDCTL32.DLL - Diagnostic utility component	
 GRDDRV32.CPL - Guardant Control Panel Applet
 GRDDRV32.DLL - Driver management library (equivalent to instdrv.dll)


Guardant driver API sample & library:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 INST.DLL\MK_DEMO.BAT  - Batch file for compilation
 INST.DLL\GRD_KEY.BMP  - Bitmap picture
 INST.DLL\DIALOG.C     - Dialogue module source text
 INST.DLL\INSTDRV.C    - Main module source text
 INST.DLL\INSTDRV.DLL  - Guardant drivers API library
 INST.DLL\INSTDEMO.EXE - Application sample
 INST.DLL\INSTDRV.H    - Header file 
 INST.DLL\INSTDRVF.H   - Header file containing function 
                         descriptions
 INST.DLL\INSTDRVS.H   - Header file containing structure and 
                        return codes descriptions
 INST.DLL\INSTSTR.H    - Header file containing string 
                        resources descriptions
 INST.DLL\INSTDRV.ICO  - Program icon
 INST.DLL\INSTDEMO.IDE - Project file for Borland C++ 5.02
 INST.DLL\INSTDMS.LIB  - Import library for INSTDRV.DLL (Microsoft)
 INST.DLL\INSTDRV.LIB  - Import library for INSTDRV.DLL (Borland)
 INST.DLL\INSTDEMO.MAK - MAKE-file for compilation
 INST.DLL\INSTDRV.RC   - Resource compiler file



-----------------------------------------------------
2     Guardant Driver Installation/Update 
-----------------------------------------------------

      -------------------------------------------------------------
        ATTENTION !!!                                                  

      * Do not connect USB dongles until Guardant driver is installed.
      * Guardant USB driver must be installed by INSTDRV.EXE utility 
        or by Guardant driver API only.
      * Do not use regular Windows wizard for driver installation.
      * Administrative privilege is required to install Guardant 
        driver under Windows NT/2000/XP.
      -------------------------------------------------------------


1. Close all applications and DOS sessions to avoid 
   file sharing errors.

2. Run driver setup program INSTDRV.EXE

3. To install or update Guardant driver click on [Install driver] or [Reinstall 
   driver] button. If installation is completed successfully, INSTDRV will 
   display a message and then return to the main window.

4. If the driver installation is successful, a message box is displayed.

5. Click [OK] to continue.

6. Close INSTDRV application.

7. Restart the system if needed.



-----------------------------------------------------
3     Guardant Driver Configuration Procedure
-----------------------------------------------------

To set the parameters of installed Guardant driver, run INSTDRV utility and 
click on [Configure driver] button in the main window.
The difference between Guardant drivers' configuration procedure in Windows 
95/98/Me and NT/2000 lies in the methods of capturing ports.

Driver configuration procedure includes the following steps:
	- Assign ports to search for the dongle
	- Assign methods of capturing ports
	- Set timeout
	- Set advanced parameters.

Assigning Ports to Search for the Dongle
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In the left upper corner of the window, a list of parallel ports found on the 
computer is displayed. In Windows 95/98/Me the address of the port is displayed 
next to its name. Furthermore, in case hardware and software to be used with 
USB devices is installed on the computer, the list of ports contains 'USB' line. 
You can specify on which ports the driver should search for dongles. This is 
very helpful when you need to reduce the response time. For example, if the 
dongle is attached to LPT2 port, and the printer is attached to LPT1 port, you 
may disable the search of the dongle on LPT1 port. If you only use Guardant USB 
dongles, you may disable the search of dongles across all LPT ports. 
By default, the search is enabled across all USB and LPT ports.

Assigning Methods of Capturing the Port
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Parallel port capture helps to avoid conflicts in case the protected 
application attempts to access the key when another application uses the same 
port (for example, during printing). The port is captured by the driver only 
for the period of communicating with the key, after which the port is released.
By default, configuration utility sets automatic capture method. Other methods 
are good for experienced users only, who would know the tricks of working with 
operating systems and peripheral devices. You may assign a combination of 
capture methods for each of the selected parallel ports.

Setting Timeout
~~~~~~~~~~~~~~~
In case the port that Guardant driver tries to access appears captured, the 
driver will wait for the port to be released. This waiting period of the driver 
is called 'timeout'. During this time, the driver will constantly check the 
status of the port, and if the latter remains captured, error #24 (Port busy) 
will be returned. Timeout period in seconds is specified in the lower part of 
the window. Allowed value ranges between 0.001 and 600 seconds. Default timeout 
value is 10.

Important: Timeout period is understood as the overall waiting time for all 
ports and not per each port (for example, the default timeout of 10 seconds 
means the total time, but not 10 seconds per each port).

Setting Advanced Parameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Advanced parameters allow you to set timer type to be used by Guardant drivers, 
as well as specify a method for generating delays that are necessary when 
communicating with the dongle. Also, there is the possibility to adjust 
base addresses of LPT ports manually when working with non-standard port 
addresses.

1. Setting timer type and specifying a method for generating delays.
   This may be required when working on old or unstable computers (for example, 
   'overclocked' computers), which often experience problems with system 
   timers. This will help to achieve maximum stability of communication with 
   Guardant dongles. For those who are not too well familiar with the design of 
   PCs, an automatic mode (set by default) is provided for selecting parameters. 
   In this case, the driver gathers statistics, analyzes stability of computer 
   timers and chooses an optimal setting.

2. Setting base addresses of LPT ports.
   Starting from version 4.52 Guardant driver supports possibility to specify
   base addresses of LPT ports used for the dongles. By default, in the 'Auto'
   mode driver automatically detects LPT base addresses. Detected addresses are
   displayed in corresponding fields. Manual address adjustment is used when
   the driver fails to detect correct address automatically.

After setting all necessary parameters press [Ok]; to cancel changes press 
[Cancel].

During the first INSTDRV session, while Guardant driver is not installed in the 
system, the default parameter values are read from INSTDRV.INI file located in 
the same directory as the installer. All parameters that you specified are 
written into the system registry and are further read from there both by 
Guardant driver and INSTDRV utility.
No system reboot is needed after reconfiguration. All changes come 
into effect immediately.



Diagnostics
~~~~~~~~~~~
Starting from version 4.7 Guardant driver is integrated with diagnostic 
utility GRDDIAG.EXE. To run diagnostic utility click on [Diagnostics]
button in 'Guardant driver configuration' window.

By default, Demo version of the diagnostic utility GrdDem32.exe is 
included to Guardant drivers package. This limited version is able 
to diagnose DEMO dongles only.

For providing access to full-featured diagnostics from driver control panel 
GrdDiag.exe must be launched  from it's home directory. Drivers must be 
installed before.
To install GrdDiag.exe in quiet mode use /REG command line parameter and 
use /UNREG for uninstalling.
(...\GrdDiag.exe /REG to install and ...\GrdDiag.exe /UNREG to uninstall)



-----------------------------------------------------
4     Guardant Driver Uninstall
-----------------------------------------------------

To uninstall the driver from the system, run INSTDRV utility and click on 
[Uninstall driver] button in the main window.

Important: in Windows 95/98/Me after the driver is removed, it remains active 
until the system is restarted. Only driver load instruction is removed from the 
system registry. All previously set driver configuration (such as ports to be 
used, methods of their capture, timeout value) are preserved.

-----------------------------------------------------
5     INSTDRV Command Line Options and Error Codes
-----------------------------------------------------

Command Line Options
~~~~~~~~~~~~~~~~~~~~

   /H, /?	Display message box with a list of available options.
   /U		Uninstall the driver (should be used with /Q option, 
                otherwise you will be returned to the main window, 
                where you should click on [Uninstall driver]).
   /I		Report in detail of all existing errors. This option 
                is better be used in emergency only, since it also 
                reports of non-fatal errors that do not affect the 
                result of the operation (for example, if INI file is 
                not found the default parameters are set).
   /LE, /LR	Enforce setting of the language for messages 
                (/LE - English, /LR - Russian). By default, the 
                language is automatically subject to active code page 
                number, and all messages and dialogues are displayed 
                in the local language.
   /RB		Ignore /Q option when a prompt for system reboot is 
                displayed (if /Q option is specified and /RB option is 
                not, then if system reboot is needed INSTDRV will carry 
                it out without any prompts, which is not always convenient).
   /NORB	Disable automatic reboot of the system.
   /Q		Do not display anything on the screen. This option is useful
                when starting INSTDRV from other applications. By default, 
                it installs the driver, and when used with /U option it 
                removes the driver.
   /LOG		Log all events to file. File _INSTDRV.LOG will be created in 
                the same folder as INSTDRV.EXE. If the file cannot be created in 
                this folder, log file will be created in %SYTEMROOT%\SYSTEM 
                folder for Windows 95/98/Me or in %SYSTEMROOT%\SYSTEM32\DRIVERS 
                folder for Windows NT/2000/XP

Error Codes
~~~~~~~~~~~

   0	Success.
   1	The operation has been interrupted by user.
   2	Attempt has been made to install the driver in environment 
        other than Windows 95/98/Me or Windows NT/2000.
   3	Error occurred during installation.
   4	User does not possess sufficient privilege (only in Windows NT/2000/XP).
   5	The driver is used by another application.
  -1	Code returned after a prompt (/?, /H) has been displayed.


-----------------------------------------------------
6     Problem Reports
-----------------------------------------------------

If you find any problems, please contact Aktiv Co.
Technical Support Team:

COMPANY HEADQUARTERS RUSSIA

Aktiv Co.
9a Komsomolsky prospect
Moscow, Russia 119146
Attn.:    Technical Support Team
Tel/fax:  +7 (095) 956-2280, 246-4066, 245-3158
E-mail:   guardant@guardant.com (general questions)
          hotline@guardant.com (technical support)
          sales@guardant.com (sales department)
Web-Site: http://www.guardant.com

                                        